Pre-requirements For Operator Approval
| ■ | Ensure Operator has their own trusted identity |
| ■ | Provide network architecture diagram for each market including SBC geo redundancy with 2x10G links via MAPSV, IPs, ASNs |
| ■ | Provide SBC failover logs |
| ■ | If Platform provider intends manage the implementation of network connectivity on behalf of the partner (meaning the platform provider does not have any existing network connectivity), submit a template network architecture that illustrates the SBC geo redundancy and use of MAPSV or if hosted in Azure use of MAPSV or Express Route. |
| ■ | Provide logs that illustrate BFD enabled on network links within each geo |
| ■ | Complete the OC Platform Provider Operator Journey/Customer Journey template |
| ■ | Document test cases and results for TNUpload, Call Duration (Screen shots will suffice) |
| ■ | Ensure Telco/Operator has access to ADO (requires that operator submits an ADO ticket) |
| ■ | Capture the telco/operator’s anomaly detection and monitoring habits |
| ■ | Demonstrate that each telco/operator onboarded has met all SLA metrics |
| ■ | Submit each telco/operator’s GTM plan and provide the landing page |